# While a lot of configuration in Sentry can be changed via the UI, for all
# While a lot of configuration in Sentry can be changed via the UI, for all
# While a lot of configuration in Sentry can be changed via the UI, for all
# new- style config(as of 8.0) you can also declare values here in this file
# to enforce defaults or to ensure they cannot be changed via the UI.For more
# information see the Sentry documentation.

###############
# Mail Server #
###############

mail.backend: 'smtp'  # Use dummy if you want to disable email entirely
mail.host: 'smtp.qq.com'
mail.port: 465
mail.username: '2582518609@qq.com'
mail.password: 'bpyblvrcekisdjfb'
mail.use - tls: false
mail.use - ssl: true

# NOTE: The following 2 configs(mail.from and mail.list - namespace) are set
#       through SENTRY_MAIL_HOST in sentry.conf.py so remove those first if
#       you want your values in this file to be effective!


# The email address to send on behalf of
mail.from: '2582518609@qq.com'

# The mailing list namespace for emails sent by this Sentry server.
# This should be a domain you own(often the same domain as the domain
# part of the`mail.from` configuration parameter value) or`localhost`.
# mail.list - namespace: 'localhost'

# If you'd like to configure email replies, enable this.
# mail.enable - replies: true

# If you'd like to configure email replies, enable this.
# mail.enable - replies: true

# When email - replies are enabled, this value is used in the Reply - To header
# mail.reply - hostname: ''

# If you're using mailgun for inbound mail, set your API key and configure a
# route to forward to / api / hooks / mailgun / inbound /
# Also don't forget to set `mail.enable-replies: true` above.
# mail.mailgun - api - key: ''

###################
# System Settings #
###################

# If this file ever becomes compromised, it's important to generate a new key.
# Changing this value will result in all current sessions being invalidated.
# A new key can be generated with `$ sentry config generate-secret-key`
system.secret - key: 'istsD>#4r,in(Z0qMHDqJ1.g;%j5_\+MK/+dV8<69AT^qk]Xuo'

# The ``redis.clusters`` setting is used, unsurprisingly, to configure Redis
# clusters.These clusters can be then referred to by name when configuring
# backends such as the cache, digests, or TSDB backend.
# redis.clusters:
#   default:
#     hosts:
#       0:
#         host: 127.0.0.1
#         port: 6379

################
# While a lot of configuration in Sentry can be changed via the UI, for all
# While a lot of configuration in Sentry can be changed via the UI, for all

transaction - events.force - disable - internal - project: true

######################
# GitHub Integration #
######################

# github - login.extended - permissions: ['repo']
# github - app.id: GITHUB_APP_ID
# github - app.name: 'GITHUB_APP_NAME'
# github - app.webhook - secret: 'GITHUB_WEBHOOK_SECRET' # Use only if configured in GitHub
# github - app.client - id: 'GITHUB_CLIENT_ID'
# github - app.client - secret: 'GITHUB_CLIENT_SECRET'
# github - app.private - key: |
#----- BEGIN RSA PRIVATE KEY-----
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#   privatekeyprivatekeyprivatekeyprivatekey
#----- END RSA PRIVATE KEY-----

#####################
# Slack Integration #
#####################

# Refer to https://develop.sentry.dev/integrations/slack/ for setup instructions.

# slack.client - id: < 'client id' >
# slack.client - secret: <client secret>
  # slack.signing-secret: <signing secret>
    ## If legacy-app is True use verfication-token instead of signing-secret
    # slack.verification-token: <verification token>
